Systems, devices, and methods for controlling access to a secure space

ABSTRACT

Systems, devices, and methods for controlling access to a secure space are disclosed. The system includes a locking device fastenable to an access point of the secure space, a server, and a network for communication between the locking device and server. The server includes a storage unit to store authorization data for the locking device and the user computing device, and a processing unit for receiving a request from the user computing device to access the locking device; authenticating the user computing device; generating authorization data; and providing at least part of the authorization data to each of the locking device and the user computing device. The locking device includes an actuator, a memory, and a processing unit for receiving a security command from the user computing device; determining whether the security command includes requesting data that corresponds to the authorization data; and generating a control signal for the actuator to move the locking device based on the security command.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication No. 63/056,539 entitled SYSTEMS, DEVICES, AND METHODS FORCONTROLLING ACCESS TO A SECURE SPACE, filed Jul. 24, 2020, the entiretyof which is incorporated herein by reference.

FIELD

The described embodiments relate to physical security and in particular,to systems, devices and methods of providing controlling access to asecure space.

BACKGROUND

Self-storage facilities rent space to tenants for storage of goods.Tenants may be individuals who would like to store household goods.Tenants may also be businesses who require space to store inventory,tools, parts, supplies, or records. Furthermore, some self-storagefacilities offer climate controlled environments, which allow businessesto readily store sensitive goods (i.e., pharmaceuticals and electronics)without the overhead expenses involved in establishing and maintainingsuch a climate controlled environment.

Self-storage units can be secured by a locking device. The lockingdevice can be provided by the tenant and personnel of the facility maynot have access to the self-storage unit. In other cases, the lockingdevice can be provided by the facility and the facility can have amaster key to unlock the locking device if needed. Locking devices canbe locked and/or unlocked with physical keys including traditionalphysical keys, key fobs, and key cards, digital keys including passwordsand key codes, or biometric data. The facility can also have additionalsecurity measures such as locked doors and gateways for areas within andaround the facility to ensure that only authorized personnel have accessto those areas of the facility.

SUMMARY

The various embodiments described herein generally relate to methods(and associated systems and devices configured to implement the methods)for controlling access to a secure space.

In a broad aspect, a system for controlling access to a secure space isdisclosed. The system includes at least one communication network; alocking device fastenable to an access point of the secure space, thelocking device comprising an actuator, a lock processor, a lock memory,and at least one lock communication interface, the actuator for movingthe locking device into a locked state to maintain the access pointclosed or an unlocked state to allow the access point to be opened, thelock processor operable to generate a control signal for the actuator,the at least one lock communication interface being operable tocommunicate via the at least one communication network; and a servercomprising: a server storage unit to store authorization data for thelocking device; at least one server communication interface operable tocommunicate with the locking device and at least one user computingdevice via the at least one communication network; and a serverprocessing unit operable to: receive, from a user computing device ofthe at least one user computing device, a request to access the lockingdevice; authenticate the user computing device; generate authorizationdata for the locking device and the user computing device; and provideat least part of the authorization data to each of the locking deviceand the user computing device; wherein the lock processor is operableto: store the authorization data from the server in the lock memory;receive a security command from the at least one user computing device;determine whether the security command includes requesting data thatcorresponds to the authorization data stored in the lock memory; and inresponse to determining that the requesting data corresponds to theauthorization data stored in the lock memory; generate a control signalfor the actuator to move the locking device into the locked state whenthe locking device transitions from open to closed, otherwise generate acontrol signal for the actuator based at least in part on the securitycommand.

In some aspects, the security command can include either an unlockcommand or a lock command; upon receipt of an unlock command, thecontrol signal generated by the lock processor can include a signal tomove the locking device into the unlocked state; and upon receipt of alock command, the control signal generated by the lock processor caninclude a signal to move the locking device into the locked state.

In some aspects, the authorization data can include a public key of apublic/private key pair of the locking device, the private key pair ofthe locking device being stored in the lock memory.

In some aspects, the authorization data can include a public key of apublic/private key pair of the user computing device, the private keypair of the user computing device being stored in memory of the usercomputing device.

In some aspects, the authorization data provided to the locking deviceand the user computing device can include a digital access key, thedigital access key including a pre-determined usage limit; and the lockprocessor can be operable to determine whether the digital access key isvalid based on the pre-determined usage limit.

In some aspects, the digital access key can include at least one of apre-determined expiration date or a pre-determined expiration period andthe lock processor can be operable to determine whether the digitalaccess key is valid based on at least one of the pre-determinedexpiration date and the pre-determined expiration period.

In some aspects, the authorization data can include a digital access keyincluding at least one of a generation date or a pre-determined startdate; and the lock processor can be operable to determine whether the adigital access key is valid based on at least one the generation date orthe pre-determined start date.

In some aspects, the authorization data can include a digital access keysigned using a certificate; and the lock processor can be operable todetermine whether the digital access key is valid based on thecertificate used to sign the digital access key.

In some aspects, the certificate can be generated by a certificateauthority of a plurality of sequential certificate authorities.

In some aspects, the server processing unit operable to authenticate theuser computing device can involve generating an invitation token havinga pre-determined expiration period, sending the invitation token to theuser computing device, and receiving the invitation token within thepre-determined expiration period.

In a broad aspect, a method for controlling access to a secure space isdisclosed. The method includes providing at least one communicationnetwork and a server, the server comprising a server processing unit, aserver storage unit, and at least one communication interface operableto communicate with at least one user computing device via the at leastone communication network; fastening a locking device to an access pointof the secure space, the locking device comprising an actuator, a lockprocessor, a lock memory, and at least one lock communication interface,the actuator for moving the locking device into a locked state tomaintain the access point closed or an unlocked state to allow theaccess point to be opened, the at least one lock communication interfacebeing operable to communicate with the server via the at least onecommunication network; storing authorization data for the locking deviceon the server storage unit; configuring the server processing unit to:receive, from a user computing device of the at least one user computingdevice, a request to access the locking device; authenticate the usercomputing device; generate authorization data for the locking device andthe user computing device; and provide at least part of theauthorization data to each of the locking device and the user computingdevice; and configuring the lock processor to: store the authorizationdata from the server in the lock memory; receive a security command fromthe at least one user computing device; determine whether the securitycommand includes requesting data that corresponds to the authorizationdata stored in the lock memory; and in response to determining that therequesting data corresponds to the authorization data stored in the lockmemory; generate a control signal for the actuator to move the lockingdevice into the locked state when the locking device transitions fromopen to closed, otherwise generate a control signal for the actuatorbased at least in part on the security command.

In some aspects of the method, the security command can include eitheran unlock command or a lock command; and configuring the lock processorcan involve configuring the lock processor to: generate a signal to movethe locking device into the unlocked state upon receipt of an unlockcommand; and generate a signal to move the locking device into thelocked state upon receipt of a lock command.

In some aspects of the method, the authorization data can include apublic key of a public/private key pair of the locking device, theprivate key pair of the locking device being stored in the lock memory.

In some aspects of the method, the authorization data can include apublic key of a public/private key pair of the user computing device,the private key pair of the user computing device being stored in memoryof the user computing device.

In some aspects of the method, the authorization data provided to thelocking device and the user computing device can include a digitalaccess key, the digital access key including a pre-determined usagelimit; and the lock processor can be operable to determine whether thedigital access key is valid based on the pre-determined usage limit.

In some aspects of the method, the digital access key can include atleast one of a pre-determined expiration date or a pre-determinedexpiration period, the lock processor can be operable to determinewhether the digital access key is valid based on at least one of thepre-determined expiration date and the pre-determined expiration period.

In some aspects of the method, the authorization data can include adigital access key including at least one of a generation date or apre-determined start date; and configuring the lock processor caninvolve configuring the lock processor to determine whether the adigital access key is valid based on at least one the generation date orthe pre-determined start date.

In some aspects of the method, the authorization data can include adigital access key signed using a certificate; and configuring the lockprocessor can involve configuring the lock processor to determinewhether the digital access key is valid based on the certificate used tosign the digital access key.

In some aspects of the method, the certificate can be generated by acertificate authority of a plurality of sequential certificateauthorities.

In some aspects of the method, configuring the server processing unit toauthenticate the user computing device can involve configuring theserver processing unit to generate an invitation token having apre-determined expiration period, send the invitation token to the usercomputing device, and receive the invitation token within thepre-determined expiration period.

In a broad aspect, a locking device is disclosed. The locking deviceincludes a body including: a rotatable locking cam having a lockedpaddle and an unlocked paddle, the rotatable locking cam being rotatablebetween a locked position and an unlocked position; a locking pin; and apower supply for supplying electrical power to circuit components of thelocking device; and a shackle having two arms insertable into the body,one of the two arms having a groove in a bottom portion thereofconfigured to engage with the locking pin when the rotatable locking camis in the locked position and the shackle is in a closed position;wherein the locking device is configured to detect a position of one ormore of the rotatable locking cam, the locking pin and the shackle.

In a broad aspect, a locking device is disclosed. The locking deviceincludes a body including a rotatable locking cam having a locked paddleand an unlocked paddle, the cam being rotatable between a first positionand a second position; a locking pin; and a power supply for supplyingelectrical power to circuit components of the locking device; and ashackle having two arms insertable into the body, one of the two armshaving a groove in a bottom portion thereof configured to engage withthe locking pin when the shackle is in a closed position; wherein in thefirst position, the locked paddle of the rotatable locking cam engagesthe locking pin to retain the locking pin in the groove and in thesecond position the locked paddle of the rotatable locking cam isdisengaged from the locking pin.

In some aspects, the locking pin is configured to fall out of the grooveof the shackle when the rotatable locking upon the shackle movingupwardly relative to the locking pin.

In some aspects, the body includes one or more switches configured toindicate if the shackle is in an open or a closed position.

In some aspects, the body includes two switches, one positioned ateither end of the shackle to indicate if the shackle is in an open or aclosed position.

In some aspects, the switches are two stage switches.

In some aspects, the body further includes a spring ball plunger and theshackle further includes a raceway, the spring ball plunger beingconfigured to rest within the raceway to provide for the shackle to beremoved from the body.

In some aspects, each of the unlocked paddle and the locked paddleextend from the rotatable locking cam towards a same arm of the shackle.

In some aspects, the locked paddle is positioned vertically above theunlocked paddle.

In some aspects, the rotatable locking cam is configured to rotate in afirst direction to move the locking device from a locked state to anunlocked state and a second direction to move the locking device from anunlocked state to a locked state.

BRIEF DESCRIPTION OF THE DRAWINGS

Several embodiments will now be described in detail with reference tothe drawings, in which:

FIG. 1A is a diagram of a system for controlling access to a securespace, according to at least one embodiment;

FIG. 1B is a diagram of a system for controlling access to a securespace, according to at least another embodiment;

FIG. 2 is an example method for providing controlling access to a securespace, according to at least one embodiment;

FIG. 3 is an illustration of an example scenario for requesting accessto a secure space, according to at least one embodiment;

FIGS. 4A and 4B are illustrations of an example method for accessing asecure space, according to at least one embodiment;

FIG. 5 is an illustration of data that can be made available by thesystem, according to at least one embodiment;

FIG. 6 is an illustration of different statuses that secure spaces canhave, according to at least one embodiment;

FIG. 7 is an illustration of different permissions to the secure spaces,according to at least one embodiment;

FIG. 8 is an illustration of a district management having control ofmultiple sites, according to at least one embodiment;

FIG. 9A is a perspective view of a locking device, according to at leastone embodiment;

FIG. 9B is a top down view of the locking device of FIG. 9A;

FIG. 9C is a front view of the locking device of FIG. 9A;

FIG. 9D is a side view of the locking device of FIG. 9A;

FIG. 9E is a cross-sectional view of the locking device of FIG. 9A alongthe line A-A in FIG. 9D, the cross-sectional view showing the lockingdevice in a locked state with its locking pin in a closed position,according to at least one embodiment;

FIG. 10 is a cross-sectional view of the locking device of FIG. 9A alongthe line A-A in FIG. 9D, the cross-sectional view showing the lockingdevice in an unlocked state with its locking pin in its closed position,according to at least one embodiment;

FIG. 11 is a cross-sectional view of the locking device of FIG. 9A alongthe line A-A in FIG. 9D, the cross-sectional view showing the lockingdevice in an unlocked state with its locking pin in its open position,according to at least one embodiment;

FIG. 12 is a cross-sectional view of the locking device of FIG. 9A alongthe line A-A in FIG. 9D, the cross-sectional view showing the lockingdevice in an unlocked state with its locking pin in its open positionand its shackle in its open position, according to at least oneembodiment;

FIG. 13 is a cross-sectional view of the locking device of FIG. 9A alongthe line A-A in FIG. 9D, the cross-sectional view showing the lockingdevice in an unlocked state with its locking pin in its open positionand its shackle in its open position and cut, according to at least oneembodiment;

FIG. 14 is a switch status diagram showing the outcomes of variouscombinations of the switches shown in FIG. 13;

FIG. 15A is a cross-sectional view of a locking device according toanother embodiment, the cross-sectional view showing the drive system ofthe locking device;

FIG. 15B is a cross-sectional view of the locking device of FIG. 15Ashowing the reversed view relative to the view shown in FIG. 15A;

FIG. 16A is a cross-sectional view of a locking device according toanother embodiment, the cross-sectional view showing a spring ballplunger of the locking device according to one embodiment; and

FIG. 16B is a collection of three perspective views of a shackle havinga raceway of the locking device of FIG. 16A, according to oneembodiment.

The drawings, described below, are provided for purposes ofillustration, and not of limitation, of the aspects and features ofvarious examples of embodiments described herein. For simplicity andclarity of illustration, elements shown in the drawings have notnecessarily been drawn to scale. The dimensions of some of the elementsmay be exaggerated relative to other elements for clarity. It will beappreciated that for simplicity and clarity of illustration, whereconsidered appropriate, reference numerals may be repeated among thedrawings to indicate corresponding or analogous elements or steps.

DESCRIPTION OF EXAMPLE EMBODIMENTS

The various embodiments described herein generally relate to methods(and associated systems configured to implement the methods) forcontrolling access to a secure space. The term “secure space”, as usedherein, broadly refers to any physical space or unit of a centralmanager and designated for use by authorized users and to which accessby unauthorized users is prevented by a locking device.

For example, the secure space can be a self-storage unit within aself-storage facility. In other embodiments, the secure space can bemultiple individual units of physical space that share a centralizedmanagement system and each individual unit is accessible to differentusers. For example, the secure space can be lockers, rooms, orcontainers, equipment locks (e.g., bikes, skis, golf clubs) locatedwithin an apartment building, condominium, office space, transit hub(e.g., airports, train stations, bus stations), hotel, resort, school,campus, recreation center, community center, library, or hospital.

As can be seen from these examples of secure space, the duration that auser is authorized by the central manager can be limited. Self-storageunits are typically rented on a monthly basis. Other forms of securespace can also be used for shorter or longer durations. For example,equipment locks may be rented on a daily basis.

A user, or a tenant of a secure space may want to allow someone else toaccess their secure space. A locking device requiring biometric datacannot be easily unlocked by other individuals. That is, the ability tounlock the device cannot be transferred amongst individuals.

A locking device requiring a physical key can be convenient as anyone inpossession of the physical key can unlock the device. However, physicalkeys must be physically transferred between individuals. In addition,physical keys can be lost, stolen, and in some cases, replicated.Physical keys do not offer traceability in respect of identifying whohas used the physical key.

The term “physical key”, as used herein, broadly refers to any physicalobject that a locking device requires presentation of in order totransition to/from a locked state and an unlocked state. A physical keycan include, but is not limited to, traditional physical keys, key fobs,and key cards, including barcodes, magnetic stripes, microchips, and/orradio frequency identification devices.

A locking device requiring a digital key can be convenient as anyone inpossession of the digital key can gain unlock the device. However, oncea digital key is shared, the ability to unlock the device can only berevoked by changing the password or key code.

In addition, in some cases, the central manager may need to unilaterallytake control of a secure space. In the case of a self-storage unit, theself-storage facility may need to block access to a self-storage unit orevict a tenant for failure to pay rental fees or other violations of arental agreement. For example, rental agreements typically prohibitself-storage units from being used as a place of residence.

To block access to a self-storage unit, an overlock can be installed onthe self-storage unit. An overlock involves placing an extra lock on thelocking device to prevent the locking device from allow access to theauthorized user. When a self-storage facility evicts a tenant, theself-storage facility may vacate the tenant's contents, includingselling the tenant's contents.

Care must be taken to ensure that such unilateral actions are beingtaken against the correct self-storage unit. Multiple individual unitscan look identical and identification of individual units can be subtle.Evicting the wrong unit will typically require compensation to theinnocent tenant, thus resulting in financial losses for the centralmanager.

The central manager may rely on employees or other individuals to carryout such actions against a secure space. However, whether for innocentreasons or for other motives, such individuals may not strictly adhereto the central manager's instructions. For example, an employee mayprovide a tenant access to the secure space after an overlock has beeninstalled. The employee may be convinced by the tenant that the overlockwas placed in error. Alternatively, the employee may be financiallyinduced by the tenant. In any event, such actions may not align with theobjectives of the central manager.

Self-storage facilities are often located in remote locations that aremay not be equipped with fast, reliable connectivity. Furthermore,self-storage facilities are often concrete buildings that can be abarrier for Wi-Fi signals. As such, systems of providing controllingaccess to a secure space requiring a communication network can encounterhigh latency, which can result in an undesirable delay in providingaccess to, or securing, a self-storage unit.

It will be appreciated that numerous specific details are set forth inorder to provide a thorough understanding of the example embodimentsdescribed herein. However, it will be understood by those of ordinaryskill in the art that the embodiments described herein may be practicedwithout these specific details. In other instances, well-known methods,procedures and components have not been described in detail so as not toobscure the embodiments described herein. Furthermore, this descriptionand the drawings are not to be considered as limiting the scope of theembodiments described herein in any way, but rather as merely describingthe implementation of the various embodiments described herein.

It should be noted that terms of degree such as “substantially”, “about”and “approximately” when used herein mean a reasonable amount ofdeviation of the modified term such that the end result is notsignificantly changed. These terms of degree should be construed asincluding a deviation of the modified term if this deviation would notnegate the meaning of the term it modifies.

In addition, as used herein, the wording “and/or” is intended torepresent an inclusive-or. That is, “X and/or Y” is intended to mean Xor Y or both, for example. As a further example, “X, Y, and/or Z” isintended to mean X or Y or Z or any combination thereof.

The terms “including,” “comprising” and variations thereof mean“including but not limited to,” unless expressly specified otherwise. Alisting of items does not imply that any or all of the items aremutually exclusive, unless expressly specified otherwise. The terms “a,”“an” and “the” mean “one or more,” unless expressly specified otherwise.

As used herein and in the claims, two or more elements are said to be“coupled”, “connected”, “attached”, or “fastened” where the parts arejoined or operate together either directly or indirectly (i.e., throughone or more intermediate parts), so long as a link occurs. As usedherein and in the claims, two or more elements are said to be “directlycoupled”, “directly connected”, “directly attached”, or “directlyfastened” where the element are connected in physical contact with eachother. None of the terms “coupled”, “connected”, “attached”, and“fastened” distinguish the manner in which two or more elements arejoined together.

The terms “an embodiment,” “embodiment,” “embodiments,” “theembodiment,” “the embodiments,” “one or more embodiments,” “someembodiments,” and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s),” unless expressly specifiedotherwise.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments described herein.

Further, although process steps, method steps, algorithms or the likemay be described (in the disclosure and/or in the claims) in asequential order, such processes, methods and algorithms may beconfigured to work in alternate orders. In other words, any sequence ororder of steps that may be described does not necessarily indicate arequirement that the steps be performed in that order. The steps ofprocesses described herein may be performed in any order that ispractical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle.

The embodiments of the systems and methods described herein may beimplemented in hardware or software, or a combination of both. Theseembodiments may be implemented in computer programs executing onprogrammable computers, each computer including at least one processor,a data storage system (including volatile memory or non-volatile memoryor other data storage elements or a combination thereof), and at leastone communication interface. For example and without limitation, theprogrammable computers may be a server, network appliance, embeddeddevice, computer expansion module, a personal computer, laptop, personaldata assistant, cellular telephone, smart-phone device, tablet computer,a wireless device or any other computing device capable of beingconfigured to carry out the methods described herein.

In some embodiments, the communication interface may be a networkcommunication interface. In embodiments in which elements are combined,the communication interface may be a software communication interface,such as those for inter-process communication (IPC). In still otherembodiments, there may be a combination of communication interfacesimplemented as hardware, software, and combination thereof.

Program code may be applied to input data to perform the functionsdescribed herein and to generate output information. The outputinformation is applied to one or more output devices, in known fashion.

Each program may be implemented in a high level procedural or objectoriented programming and/or scripting language, or both, to communicatewith a computer system. However, the programs may be implemented inassembly or machine language, if desired. In any case, the language maybe a compiled or interpreted language. Each such computer program may bestored on a storage media or a device (e.g. ROM, magnetic disk, opticaldisc) readable by a general or special purpose programmable computer,for configuring and operating the computer when the storage media ordevice is read by the computer to perform the procedures describedherein. Embodiments of the system may also be considered to beimplemented as a non-transitory computer-readable storage medium,configured with a computer program, where the storage medium soconfigured causes a computer to operate in a specific and predefinedmanner to perform the functions described herein.

Furthermore, the system, processes and methods of the describedembodiments are capable of being distributed in a computer programproduct comprising a computer readable medium that bears computer usableinstructions for one or more processors. The medium may be provided invarious forms, including one or more diskettes, compact disks, tapes,chips, wireline transmissions, satellite transmissions, internettransmission or downloadings, magnetic and electronic storage media,digital and analog signals, and the like. The computer useableinstructions may also be in various forms, including compiled andnon-compiled code.

Referring to FIG. 1, there is shown a diagram of a system 100 forcontrolling access to a secure space, according to at least oneembodiment. The system 100 can include one or more locking devices 110for one or more secure spaces, a server 120, a communication network130, and a user computing device 140. Although only two locking devices110 a and 110 b are shown in FIG. 1, it is possible for the system 100to include fewer or more locking devices 110.

Similarly only one user computing device 140 is shown in FIG. 1 but itis possible for the system 100 to include more user computing device140. The user computing device 140 can be associated with a tenant or acentral manager, including personnel located on-site or off-site such asemployees, site managers, and corporate administrators.

Although only one server 120 is shown in FIG. 1, it is possible for thesystem 100 to include one or more servers 120 that may be distributedover a wide geographic area and connected via the communication network130.

Access to a secure space can be controlled by one or more lockingdevices 110. For example, a first locking device 110 a can provideaccess to the site or the facility; a second locking device 110 b canprovide access to a particular floor of the facility; and a thirdlocking device 110 can provide access to an individual unit on thatfloor of the facility.

The locking device 110 can secure access to a physical space at anaccess point. The term “access point”, as used herein, broadly refers toan entrance of a secure space that has an open state for permittingaccess to the secure space from the access point and a closed state forpreventing access to the secure space from the access point. An accesspoint can be a door, a gate, a fence, two adjacent pieces of housing, orany other type of enclosure.

The locking device 110 can include a shackle for engaging with, orfastening to, a clasp on an access point of the physical space to keepthe access point closed. The access point can be opened by disengagingthe shackle from the clasp on the access point. In other embodiments,the locking device 110 may be directly fastened to the access point.

As shown in FIG. 1, the locking device 110 a can include a lockprocessing unit 114, a lock memory (or data storage component) 112, alock communication interface 116, and an actuator 118. The lockprocessing unit 114 facilitates the operation of the actuator 118 byproviding a control signal for the actuator 118. The lock processingunit 114 can include any suitable processors, controllers or digitalsignal processors that can provide sufficient processing power dependingon the configuration, purposes and requirements of the locking device110. In some embodiments, the lock processing unit 114 can include morethan one processing unit with each processing unit being configured toperform different dedicated tasks.

The lock memory 112 can store data to be used during the operation ofthe locking device 110 and/or to facilitate the operation of the lockingdevice 110. Example data can include identification data for the lockingdevice 110. Identification data can represent a model or type of thelocking device 110. The identification data can also represent anidentifier for that particular locking device 110. For example, theidentification data can include, but is not limited to a LoRa MACaddress. Identification data for the locking device 110 can beprovisioned to the locking device 110 at the time that the lockingdevice 110 is manufactured.

The lock memory 112 can also store authorization data for the lockingdevices 110 and the user computing devices 140. The authorization datacan include one or more digital keys for the locking device 110 itself,the server 120, and for user computing devices 140 authorized to accessthe locking device 110. For example, at the time that the locking device110 is manufactured, a public key of a public/private key pair belongingto the server 120 can be provisioned to the locking device 110 andstored in the lock memory 112. In addition, at the time that the lockingdevice 110 is manufactured, the lock processing unit 114 can alsogenerate a public/private key pair for the locking device 110. Thelocking device 110 can store the private key of its own public/privatekey pair in the lock memory 112 and provide the public key of its ownpublic/private key pair to the server 120. The lock memory 112 can storea digital key identifier that can be unique for each digital access key.The digital key identifier can track each digital access key issued. Theserver 120 can provide the digital key identifier along with apre-determined usage limit for that digital access key to the lockingdevice 110. For each digital access key, the lock memory 112 can alsostore a local usage count. The local usage count for each digital accesskey can track the number of times each digital access key is used. Thelocal usage count can be an integer number that is increased each timethe digital access key is used.

The lock memory 112 can also store operating data of the locking devices110. Operating data can relate to an operating state of the lockingdevices 110, such as a locked state, an unlocked state, an open state,and a closed state. Operating data of the locking devices 110 can alsorelate to an operating mode of the locking devices 110 such as a regularpower mode or a low power mode. Operating data can also relate tomovement of the locking device 110, attempted openings of the lockingdevice 110, and a state of charge of an electrical energy storage unitof the locking device 110, if provided. Operating data typicallyincludes temporal information, such as the date and time of events suchas the date and time of a transition between states and/or modes.

The lock communication interface 116 can include any component forfacilitating communication with the other components of the system 100via the communication network 130. For example, the lock communicationinterface 116 can include a wireless transceiver for communicatingwithin a wireless communications network. The lock communicationinterface 116 can communicate identification data and/or operating dataof the locking devices 110 to the communication network 130. The lockcommunication interface 116 can receive commands from the communicationnetwork 130.

For example, the lock communication interface 116 can send data to theserver communication interface 126, such as, but not limited to, batterystate of charge and temperature status information, as well as lock,unlock, and tamper event information and send data to the servercommunication interface 126 such as, but not limited to, updates toauthorization data (i.e., revoking previously authorized access) andfirmware updates.

The actuator 118 can receive a control signal from the lock processingunit 114. Based on the control signal, the actuator 118 can move thelocking device 110 into the locked state or the unlocked state. When thelocking device 110 is in the locked state, the shackle can remainengaged with the clasp on the access point to keep the access pointclosed. When the locking device 110 is in the unlocked state, theshackle can be disengaged from the clasp on the access point to allowthe access point to be opened.

The lock processing unit 114 can receive a security command from a usercomputing device 140 of a user, such as a tenant or central manager,either directly or indirectly via the communication network 130. Forexample, the security command received can include an unlock command ora lock command. Upon receipt of the security command, the lockprocessing unit 114 can determine whether the security command should begranted. If the security command should be granted, the lock processingunit 114 can generate a control signal for the actuator. If the securitycommand should not be granted, the lock processing unit 114 does notgenerate a control signal for the actuator.

A security command involving an unlock command can be generated by theuser computing device 140 of a user wishing to access the self-storageunit on which the locking device 110 is fastened to. Upon receipt of anunlock command, the lock processing unit 114 can determine, based onauthorization data stored in the lock memory 112, whether the usercomputing device 140 is authorized to access the self-storage unit. Ifthe lock processing unit 114 determines that the user computing device140 is authorized to access the self-storage unit, the lock processingunit 114 can generate a control signal for the actuator 118 to move thelocking device 110 into the unlocked state. Once the locking device 110is in the unlocked state, the locking device 110 can be disengaged,removed, or positioned in a manner to allow the access point to beopened. If the lock processing unit 114 determines that the usercomputing device 140 is not authorized to access the self-storage unit,the lock processing unit 114 does not generate a control signal to movethe locking device 110 into the unlocked state.

Similarly, a security command involving a lock command can be generatedby the user computing device 140 of a user wishing to secure theself-storage unit on which the locking device 110 fastenable to. Uponreceipt of a lock command, the lock processing unit 114 can determine,based on authorization data stored in the lock memory 112, whether theuser computing device 140 is authorized to secure the self-storage unit.If the lock processing unit 114 determines that the user computingdevice 140 is authorized to secure the self-storage unit, the lockprocessing unit 114 can generate a control signal for the actuator 118to move the locking device 110 into the locked state. The lockprocessing unit 114 can also automatically generate a control signal forthe actuator 118 to move the locking device 110 into the locked statewhen the locking device 110 returns to the closed state after being inthe open state. Once the locking device 110 is in the locked state, thelocking device 110 cannot be disengaged, or positioned in a manner toallow the access point to be opened. That is, in the locked state, thelocking device 110 remains engaged with the access point to keep itclosed. If the lock processing unit 114 determines that the usercomputing device 140 is not authorized to secure the self-storage unit,the lock processing unit 114 may not generate a control signal to movethe locking device 110 into the locked state.

The determination of the locked state of the locking device 110 may notbe limited to the state of the locking device 110 in itself. In someembodiments, the locked state can also depend on a location of thelocking device 110 and the pattern, behavior, or sequence of events atthe locking device 110. The location of the locking device 110 can bedetermined by a signal strength of the locking device 110 to thecommunication network 130. In some embodiments, the location of thelocking device 110 can be determined based on the location ofneighbouring locking devices. For example, the location of the lockingdevice 110 can be determined by a comparison of the signal strength ofthe locking device 110 to the signal strength of neighbouring lockingdevices.

In some embodiments, the security command can include a lock command oran unlock command. In some embodiments, the security command does notinclude an express lock command nor an express unlock command (i.e., thesecurity command does not require data). Instead, upon receipt of asecurity command, the security command can be a command to changestates. That is, the lock processing unit 114 can determine that thecurrent state of the locking device 110 is the locked state andunderstand the security command as being an unlock command. Similarly,the lock processing unit 114 can determine the current state of thelocking device 110 is the unlocked state and understand the securitycommand as being a lock command.

In some embodiments, the security command can be manually initiated by auser interacting with the user computing device 140, that is, the userproviding input to the user computing device 140. In some embodiments,the security command can be automatically generated by the usercomputing device 140 upon establishing a communication link with thelocking device 110. In some embodiments, the security command caninclude requesting data identifying the user computing device 140.

In at least one embodiment, requesting data can be automatically sentfrom the user computing device 140 upon establishing a communicationlink with the locking device 110. Furthermore, in such cases, therequesting data can serve as a security command to change states, eitherfrom the locked state to unlocked state or from the unlocked state tothe locked state.

In addition to receiving a security command and determining whether theuser computing device 140 is authorized, the lock processing unit 114may require additional conditions to be met. For example, the lockingdevice 110 can also include a switch and the lock processing unit 114may require the switch to be manipulated in order to generate a controlsignal that causes the actuator 118 to move the locking device 110 intothe unlocked state.

In another example, the locking device 110 can also require a passwordor a key code to be entered in order to generate a control signal thatcauses the actuator 118 to move the locking device 110 into the unlockedstate. In some embodiments, the password or key code can be analternative to the security command generated by the user computingdevice 140. This can be appropriate for example, when the locking device110 provides access to a plurality of users, such as for a site, afacility, or an entire floor.

In yet another example, the locking device 110 can include a physicalkey mechanism and the presentation of the physical key can itself unlockthe locking device 110 or be required in addition to the securitycommand generated by the user computing device 140.

In addition, the lock processing unit 114 can transmit the status of thelocking device 110 to the server 120 via the communication network 130.In some embodiments such as but not limited to the alternativeembodiment system 100 b shown in FIG. 1B, the communication network 130may include more than one communication network. For instance, thelocking device 110 may receive a security command from the usercomputing device 130 via a first communication network 130 a such as butnot limited to a Bluetooth® Low Energy network and may transmit a signalsuch as a signal indicating a status of the locking device 110 to theserver 120 via a second communication network 130 b. In the embodimentshown in FIG. 1B, the second communication network is a LoRaWAN gatewaycommunication network.

In some embodiments, the locking device 110 can include a timer (notshown in FIG. 1). The timer can be activated, or initiated, when thelocking device 110 enters, or is transitioned to, an unlocked state. Thetimer can be configured to terminate when the locking device 110 in anopen state, that is, when the locking device 110 is disengaged from theaccess point. The timer can be configured to expire after apre-determined period of time that the locking device remains in aclosed state, that is, when the locking device 110 remains engaged withthe access point, after it enters that instance of the unlocked state.When the timer expires, the lock processing unit 114 can generate acontrol signal to move the locking device 110 into the locked state.

The locking device 110 can include with an electrical energy storageunit (not shown in FIG. 1) for supplying electrical power to circuitcomponents of the locking device 110. Circuit components include thelock processing unit 114 and can include the actuator 118. Theelectrical energy storage unit can be a battery. The battery can bedisposable or rechargeable. An electrical energy storage unit can beconvenient as it can eliminate the need to run wires to each accesspoint or each secure space.

In some embodiments, circuit components of the locking device 110 can besupplied with electrical power from a power supply via a wiredconnection. That is, electrical power can be supplied to the lockingdevice 110 via a wired connection.

In some embodiments, the locking device 110 can remain in the same statewhen power is not supplied to circuit components of the locking device110. That is, the locking device 110 can remain in the state immediatelyprior to power being disconnected from the circuit components. This canallow the electrical energy storage unit to be removed for maintenancewhen the locking device 110 is locked. The electrical energy storageunit can be removed and replaced, or temporarily removed for charging,if a wired charging connection is not available. The ability for thelocking device 110 to remain locked without power to circuit componentsallows discharged electrical energy storage units to be managed on an asneeded basis.

In some embodiments, the locking device 110 can operate in differentmodes, including a regular power mode and a low power mode to allow foran extended operating duration before recharging or replacement of theelectrical energy storage unit. In the regular power mode, the lockingdevice 110 may communicate operating data to the server 120 via thecommunication network 130. Such communication can occur on anevent-basis. For example, the status of the locking device 110 can betransmitted when the locking device 110 transitions from the open stateto the closed state. Such communication can also occur on a temporalbasis. For example, the status of the locking device 110 can betransmitted on a regular schedule, such hourly.

In the low power mode, the locking device 110 may not communicateoperating data to the communication network 130. In some embodiments,the locking device 110 can store the operating data in the lock memory112 during the low power mode and then transmit the operating data tothe communication network 130 in the next instance of the regular powermode.

In some embodiments, the locking device 110 in the low power mode can beswitched into the regular power mode from distinct wakeup signals fromthe communication network 130. In some embodiments, the locking device110 can include a sensor or a switch to receive user input for switchingthe locking device 110 from the low power mode to the regular powermode. For example, the sensor can detect motion representing user input,such as an accelerometer. When the locking device 110 includes a switch,the user input can also be used for switching the locking device 110from the regular power mode to the low power mode.

In some embodiments, the locking device 110 can be switched into theregular power mode at pre-determined time intervals. That is, thelocking device 110 can storing the operating data during the low powermode and wakeup (i.e., switching to the regular power mode) atpredetermined time intervals to transmit the operating data to thecommunication network 130.

In at least one embodiment, the locking device 110 is padlock capable ofwireless communication. A padlock can offer flexibility in being used indoor systems of existing buildings. Furthermore, a padlock can beconvenient as it can be interchangeable with other padlocks.

As shown in FIG. 1, the server 120 includes a server storage unit 122, aserver processing unit 124, and a server communication interface 126.The server storage unit 122 can store data generated by the serverprocessing unit and data received from the locking devices 110, usercomputing devices 140, other sensor units and output devices (not shownin FIG. 1). For example, the server storage unit 122 can store data tobe in respect of the operation of the system 100, such as identificationdata, authorization data, access management data of the locking devices110, facility data, and monitoring data of the secure space.

The server storage unit 122 can store identification data for thelocking devices 110, the storage unit on which the locking devices arefastened to, and the user computing devices 140. Identification data forthe locking devices 110 can include, but is not limited to, a LoRa MACaddress that is provisioned to the locking device 110 when the lockingdevice 110 is manufactured. Identification data for the storage unit caninclude, but is not limited to, a unit identifier for the storage unitthat the locking device 110 is fastened to. Identification data for theuser computing devices 140 can include but is not limited to an emailaddress or an SMS phone number. Identification data for the usercomputing devices 140 can be provided to the server 120 when uponenrollment by the user of the user computing device 140.

Identification data can also include tokens used for enrolling the usercomputing device 140. The server storage unit 122 can generate a tokenfor the enrollment of each user computing device 140. The token can betransmitted via an email address or an SMS phone number, inviting theuser to prove ownership of the email address or SMS phone number. Eachuser can present the received token to the server 120 in order to provethe ownership of the email address or SMS phone number. Tokens can bevalid after generation for a limited time period.

The server storage unit 122 can also store authorization data for thelocking devices 110 and the user computing devices 140. Theauthorization data can include one or more digital keys for the server120 itself, the locking devices 110, and user computing devices 140authorized to access each of the locking devices 110. For example, theserver storage unit 122 can store a private key of the public/privatekey pair belonging to the server 120 and whose public key was providedto a locking device 110 at the time of the manufacture of the lockingdevice 110. The server storage unit 112 can also store a public key ofthe public/private key pair belonging to the locking device 110. Theserver storage unit 112 can also store a private key of a public/privatekey pair for each token and whose public key was provided to a usercomputing device 140 at the time of the enrollment of a user computingdevice 140. The server storage unit 122 can also store the public key ofthe public/private key pair belonging to the user computing device 140.The server storage unit 122 can also generate and store a digital accesskey to identify users authorized to access the locking device 110. Theserver 120 can provide the digital access key to the user computingdevice 140. The server 120 can provide the digital key identifier and apre-determined usage limit to the locking device 110.

Access management data of the locking devices 110 can relate to securitycommands (including lock and unlock commands), and the operating data.Access management data typically includes temporal information, such asthe date and time of events such as the date and time that securitycommands are received. Access management data generally forms a log orledger of access for the secure space. That is, tenants and/or centralmanagers can review the access management data to determine who hasaccessed the secure space, via the security commands, and the operatingdata of the locking device 110.

Facility data can relate to the physical environment of the facility,and the location of system components within the facility including butnot limited to secure spaces, components of the communication network120 (e.g., nodes that are described below), or sensor units, and outputdevices. The location can relate to a building, wing, or floor, or otherrelevant area identifier of the facility. It should be noted thatlocations can include both indoor and outdoor locations in and aroundthe facility.

Monitoring data of the secure space can be received from other sensorunits and output devices. Monitoring data can relate to an operatingstate of an access point to which the locking device is fastened to. Theoperating state of the access point can be an open state or a closedstate. Monitoring data of the secure space can also relate to imagedata, motion data, lighting data, and heat data of the secure space

The server storage unit 122 can also store computer programs that areexecutable by the server processing unit 124. For example, the computerprograms can facilitate communication between the server 120 and thelocking devices 110. Another example computer program can be an advancedimage processing application. The server storage unit 122 can also storecomputer programs that are downloadable and executable by user computingdevices 140 to facilitate communication between the server 120 and theuser computing devices 140.

In some embodiments, the server storage unit 122 can instead be separatefrom the server 120 and be accessible to the server 120 via thecommunication network 130.

The server processing unit 124 can control the operation of the server120. The server processing unit 124 may be any suitable processingunits, controllers or digital signal processors that can providesufficient processing power depending on the configuration, purposes andrequirements of the server 120. In some embodiments, the serverprocessing unit 124 can include more than one processing unit with eachprocessing unit being configured to perform different dedicated tasks.The server processing unit 124 together with the lock processing unit114 at the locking devices 110 contribute to the control of the system100.

The server communication interface 126 facilitates communication betweenthe server 120 and the other components of the system 100, such as thelocking devices 110 and other sensor units and output devices, via thecommunication network 130. The server 120 can also connect to theInternet.

For example, the server communication interface 126 can receive datafrom the lock communication interface 116, such as, but not limited to,battery state of charge and temperature status information, as well aslock, unlock, and tamper event information and send data to the lockcommunication interface 116 such as, but not limited to, updates toauthorization data (i.e., revoking previously authorized access) andfirmware updates.

For example, the server communication interface 126 can receive datafrom the user computing device 140, such as, but not limited to,requests for authorization data, such as all currently issued digitalaccess keys for the user computing device 140, and send data to the usercomputing device 140 such as, but not limited to, authorization data(requested or otherwise), and push notifications.

Some components of the server 120 may be virtualized in a cloudcomputing infrastructure. A cloud computing infrastructure can improvereliability and maintenance of the server. A cloud computinginfrastructure can also allow a system 100 to manage client informationand provide access control across a plurality of facilities.

The locking devices 110, the user computing devices 140, and the server120 may communicate via the communication network 130. The communicationnetwork 130 may be any network capable of carrying data, including theInternet, Ethernet, plain old telephone service (POTS) line, publicswitch telephone network (PSTN), integrated services digital network(ISDN), digital subscriber line (DSL), coaxial cable, fiber optics,satellite, mobile, wireless (e.g. Wi-Fi, WiMAX, Zigbee, Z-Wave,Bluetooth®, Bluetooth® Low Energy, Long Range “LoRa”), SS7 signalingnetwork, fixed line, local area network, wide area network (e.g., LongRange Wide Area Network “LoRaWAN”), and others, including anycombination of these, capable of interfacing with, and enablingcommunication between the server 120, the locking devices 110, and usercomputing devices 140.

In some embodiments, more than one communication network 130 can beprovided. For example, the locking devices 110 and the server 120 cancommunicate via first communication network 130 while the user computingdevices 140 and the server 120 can communicate via a secondcommunication network 130. In some embodiments, some locking devices 110and/or user computing devices 140 can communicate with the server 120via a first communication network 130 while other locking devices 110and/or user computing devices 140 can communicate with the server 120using a second communication network 130.

In some embodiments, the locking devices 110 and the server 120 cancommunicate via first communication network 130; the user computingdevices 140 and the server 120 can communicate via a secondcommunication network 130; and the locking devices 110 and the usercomputing devices 140 can communicate via a third communication network130. For example, the locking devices 110 and the server 120 cancommunicate via a private Wide Area Network (“WAN”), such as but notlimited to LoRaWAN; the user computing devices 140 and the server 120can communicate via a public WAN such as but not limited a cellularnetwork or Wi-Fi; and the locking devices 110 and the user computingdevices 140 can communicate via a local point-to-point link, such asBluetooth®.

The communication network 130 can include a network of nodes. Thenetwork of nodes can include one or more nodes for transmitting andreceiving data from the components of the system 100 located in afacility, such as locking devices 110, user computing devices 140, andsensor devices. The network of nodes can be connected together. Thenetwork of nodes can be connected to the server 120. In someembodiments, the network of nodes can be connected via a wiredconnection and/or over a wireless connection. In some embodiments, nodesmay include a video camera to collect visual information of the lockingdevices and/or the environment around the locking devices. The camerasmay be a thermal camera, a digital camera, or the like. In someembodiments, the cameras may be generally maintained in a sleep stateand programmed to awake upon receiving a signal indicating that thelocking device or a door associated with a locking device has beenopened. In some embodiments, the camera may be used to confirm a statusof the door (e.g. open/closed). In some embodiments, the camera may beused to detect a thermal change in the door (e.g. detect whether thedoor is open/closed based on a thermal change).

For example, each locking device 110 and user computing device 140 maybe equipped with a wireless communication interface to enable wirelesscommunications according to a wireless protocol (e.g. LoRa, Bluetooth®,Bluetooth® Low Energy, Zigbee, or Z-Wave). Other components of thesystem 100 (e.g., sensor units and output devices) may also communicateusing the communication network 130.

In some embodiments, the communication network 130 can be physicallyconnected to the server 120. In some embodiments, the server 120 may beequipped with a wireless communication interface to enable wirelesscommunications according to a Wi-Fi protocol (e.g. IEEE 802.11 protocolor similar).

The location of nodes can be pre-determined and stored on the serverstorage unit 122 as facility data. When a node communicates datareceived from a locking device 110 and/or user computing device 140 tothe server 120, the node can also provide self-identifying data that theserver 120 uses to determine the location of the locking device 110and/or user computing device 140 from which the data originated based onthe location of the node. In some embodiments, the location of the nodecan be taken as the location of the locking device 110 and/or usercomputing device 140. In other embodiments, the location of the lockingdevice 110 and/or user computing device 140 can be determined based onthe location of a plurality of nodes. Any appropriate algorithm fordetermining the location of the locking device 110 and/or user comingdevice based on the location of a plurality of nodes can be used,including but not limited to triangulation.

In some embodiments, the other components of the system 100 can includesensor units, output devices, gate controls, door sensors, cameras,motion detectors, and lights. Sensor units can collect data from theenvironment of the secure space. For example, the one or more sensorscan include a LiDAR device (or other optical/laser, sonar, radarrange-finding such as time-of-flight sensors). The one or more sensorscan include optical sensors, such as video cameras and systems (e.g.,stereo vision). The one or more sensor units can include motion sensors,light sensors, or heat sensors.

The user computing devices 140 may be any networked device operable toconnect to the communication network 130. A networked device is a devicecapable of communicating with other devices through a network such asthe communication network 130. A networked device may couple to thecommunication network 130 through a wired or wireless connection. LoRa,Bluetooth® or Bluetooth® Low Energy are examples of a wireless protocolthat the user computing device 140 use to connect to the communicationnetwork 130.

User computing devices 140 may include at least a processing and memory,and may be an electronic tablet device, a personal computer,workstation, server, portable computer, mobile device, personal digitalassistant, laptop, smart phone, wearable device, an interactivetelevision, a video display terminal, gaming console, and portableelectronic devices or any combination of these.

The user computing device 140 can operate computer programs tofacilitate communication with the server 120 and/or communicationnetwork 130. The computer program can be downloaded from the server 120or from a third-party server, such as an application store. Once thecomputer program is downloaded onto the user computing device, it can beexecuted by the user computing device. In some embodiments, the system100 can include the computer programs that facilitate communication withthe server.

In addition, the computer programs may be specific to the type of user.That is, the computer program for a client (i.e., a tenant) can bedifferent from a computer program for a central manager (i.e., corporateadministrators, district and/or site managers). The computer program forcentral managers can have additional functionalities compared to that ofclients. For example, the central managers can access a mapping tool forillustrating status of a plurality of storage units.

In other embodiments, the user computing device 140 can operate anInternet browser to access a web portal that provides a similar functionto the computer program. That is, a web portal can be used to facilitatecommunication with the server 120.

Functions of the computer program operating on the user computing device140 to facilitate communication with the server 120 and/or communicationnetwork 130 may be dependent on its connection to the communicationnetwork 130 or a particular node of the communication network 130. Thiscan allow functions of the computer program to be disabled or enabledbased on the location of the user computing device. For example, thesubmission of a security command to unlock or lock a locking device 110,or the submission of a vacancy notice using the user computing device140 may be enabled or disabled when the user computing device 140 is oris not in communication with the communication network 130, including aparticular node or any nodes of the communication network 130.Communication with the communication network 130 can rely on the signalstrength of the user computing device 140 to the communication network130. Based on the signal strength of the user computing device 140 tothe communication network 130, the location of the user computing device140 on site or in proximity to a particular locking device 110 can bedetermined. In some embodiments, the location of the user computingdevice 140 can be determined by GPS operating on the user computingdevice.

It can be convenient to access self-storage units using a user computingdevice 140 such as a smartphone since smartphones are widely used. If atthe last minute a user requires access to their self-storage unit, theyare much more likely to have their smartphone with them than a physicalkey for their self-storage unit.

The user computing device 140 can also allow account management (i.e.,personal or corporate accounts) and payments, and/or provide the accountstatus, site status, and alerts.

As noted above, identification data for the user computing devices 140can include but is not limited to an email address or an SMS phonenumber. Proof of ownership of such data can be used as a proxy for theidentity of an individual user. In some embodiments, a method forverifying proof of ownership can involve, for example, the server 120and user computing device 140 exchanging encrypted data such as one ormore tokens.

For example, the method can begin with the server 120 generating aninvitation token and a public/private key pair for the invitation token.The invitation token can include a pre-determined expiration date andtime and the email address or SMS phone number whose ownership is beingverified. The server 120 can encrypt the invitation token using thepublic/private key pair for the invitation token and transmit theencrypted invitation token along with the public key of thepublic/private key pair for the invitation token to the individual atthe email address or the SMS phone number. The server 120 can store thepublic/private key pair for the invitation token as well as the emailaddress or the SMS phone number that the invitation token relates to inthe server storage unit 122.

The user computing device 140 can generate its own public/private keypair, and store the private key in the phone memory. The user computingdevice 140 can also retrieve an application token from the server 120.Upon receipt of the application token, the encrypted invitation tokenand public key for the invitation token from the server, the usercomputing device 140 can respond to the invitation by transmitting arequest to receive a digital access key. The request to receive adigital access key can include the application token and the invitationtoken (that was decrypted using the public key of the public/private keypair for the invitation token). The user computing device 140 canencrypt the application token and the invitation token using thepublic/private key pair for the user computing device 140. The usercomputing device 140 can transmit the encrypted application token andinvitation token along with the public key of the public/private keypair for the user computing device 140 to the server 120.

Upon receipt of the request to receive a digital access key, the server120 can verify that the invitation token is valid. The server 120 candetermine that the invitation token is valid if: the public key for theinvitation token exists in the server storage unit 122, the private keyfor the invitation token in the server storage unit 122 can decrypt theinvitation token, the pre-determined expiration date and time of theinvitation token has not passed, and the email address or the SMS phonenumber of the invitation token exists in the server storage unit 122.Upon determining that the invitation token is valid, the server 120considers ownership to be proven and can store the email address or theSMS phone number of the invitation token in relation with theapplication token. In addition, the server 120 can remove the invitationtoken and its corresponding public/private key pair from the serverstorage unit 122.

In some embodiments, the server 120 can periodically check outstandingtokens in the server storage unit to determine if they have expired. Insome embodiments, the outstanding tokens can be removed from the serverstorage unit 122. In some embodiments, the server 120 can resend theinvitation token to the email address or SMS phone number.

After proof of ownership of the email address or the SMS phone numberhas been established, the server 120 can generate and provide digitalaccess keys to the user computing device 140. For example, digitalaccess keys can be generated and provided to the user computing device140 and the locking device 110 when a tenant has extended their paidthrough date, a tenant has requested a key be delivered to a surrogate,or a manager requests a master key.

Referring now to FIG. 2A, steps for an example method of controllingaccess to a secure space is shown in a flowchart diagram 200. At step202, at least one communication network 130 and a server 120 can beprovided.

At step 204, a locking device 110 can be fastened to an access point ofthe secure space. The locking device 110 can be positioned so that inthe locked state, the locking device 110 can maintain the access pointclosed and in the unlocked state, the locking device 110 can allow theaccess point to be opened.

At step 206, the server 120 can generate authorization data for the usercomputing device 140 and store the authorization data on the lockingdevice 110 and the user computing device 140. The authorization data caninclude a digital access key. For example, the digital access key can beone of a tenant access key, a surrogate access key, and a master accesskey.

A digital access key includes a public key of a public/private key pairbelonging to the user computing device 140 and a public key of apublic/private key pair belonging to the locking device 110. Forexample, to identify the user computing device 140, the user computingdevice 140 can generate a public/private key pair upon installation of acomputer program to facilitate communication between the user computingdevice 140, the server 120, and the locking devices 110. The usercomputing device 140 can store the private key of its own public/privatekey pair in a phone memory and provide the public key of its ownpublic/private key pair to the server 120. As noted previously, the LoRaMAC address and the public key of the public/private key pair belongingto the locking device 110 was provided to the server 120 at the time thelocking device 110 was manufactured.

After receiving the public key of the user computing device 140, theserver 120 can generate a digital access key (i.e., tenant access keys,surrogate access keys, or master access keys) that includes the publickey of the user computing device 140, LoRa MAC address and the publickey of the locking device 110, and a certificate of the server 120 thatsigns the digital access key. The digital access key can be provided tothe user computing device 140.

The digital access key can also include one or more of a generationdate, a pre-determined start date, a pre-determined expiration date, apre-determined expiration period, a pre-determined usage limit, and/orthe digital key identifier. The server 120 can provide the digital keyidentifier and the pre-determined usage limit of the digital access keycan be provided to the locking device 110.

A generation date can relate to the date and time that the digitalaccess key is generated or issued. A pre-determined start date canrelate to a fixed date and time (e.g., day, month, and year) that thedigital access key will become valid. For example, a digital access keymay be generated in advance of when the tenancy will begin. In someembodiments, the pre-determined start date can be omitted and thedigital access key can become valid upon issuance.

A pre-determined expiration date can relate to a fixed date and time(e.g., day, month, and year) that the digital access key will expire.That is, the digital access key can become invalid after the expirationdate. The pre-determined expiration date is typically used with tenantaccess keys, for which access is authorized until a particular date,such as a “paid through” date.

A pre-determined expiration period can relate to a fixed duration fromissuance of the digital access key (e.g., time duration from issuance)that the digital access key is valid. That is, the digital access keycan expire after the fixed duration. The pre-determined expirationperiod is typically used with surrogate access keys (e.g., couple hoursfrom issuance) and master access keys (e.g., few minutes from issuance).

A pre-determined usage limit can relate to a fixed number of times thatthe digital access key can be used. That is, the digital access key canbecome expended after it has been used a pre-determined number of times.Pre-determined usage limit is typically used with surrogate access keys(e.g., small number of uses) and master access keys (e.g., one time use)while tenant access keys can typically be used an unlimited number oftimes. In some embodiments, the pre-determined usage limit can beconfigurable by a user computing device 140. For example, the user of auser computing device 140, such as a tenant, can select thepre-determined usage limit for a surrogate access key. The local usagecount for the digital access key can be compared against thepre-determined usage limit. If the local usage count exceeds thepre-determined usage limit, the lock processing unit 114 can determinethat the digital access key is invalid. If the local usage count doesnot exceed the pre-determined usage limit, the lock processing unit 114can determine that the digital access key is valid.

In some embodiments, the digital access key can have a combination oftwo or more of a pre-determined expiration date, a pre-determineexpiration period, as well as a pre-determined usage limit. In someembodiments, the digital access key can become invalid (i.e., expire orexpended) upon the earliest of the pre-determined expiration date, thepre-determine expiration period, and the pre-determined usage limit.

In some embodiments, the digital access key for a locking device 110 canbe reissued. The digital key identifier can be monotonically increasedfor each new reissue of a key. By tracking each issued key, keys canalso be revoked by simply reissuing a new key. For example, digitalaccess keys can be reissued when there is a new pre-determinedexpiration date (i.e., tenancy has been extended), upon request by thetenant, upon request by a manager. Digital access keys can also beautomatically reissued on a regular basis for good security practices.To revoke keys, the locking device 110 can be configured to requiredigital key identifiers be greater than a given threshold correspondingto the digital key identifier at the time of revocation.

When issuing a digital access key, a certificate authority signs thedigital access key with a certificate. The use of certificates canenhance security. The locking device 110 can reject digital access keysbased on the certificate used to sign the digital access key. Forexample, a certificates may not be valid at the time that the digitalaccess key is presented to the locking device 110. A certificate caninclude a pre-determined start date and not be valid yet at the timethat the digital access key is presented to the locking device 110. Acertificate can include a pre-determined end date and be expired by thetime the digital access key is presented to the locking device 110.

The server 120 acts as a certificate authority. As noted earlier, thesystem 100 can include one or more servers 120 that are distributed overa wide geographic area and connected via the communication network 130.As such, a plurality of certificate authorities can be used to reducethe load of key signing for a single certificate authority. In addition,a plurality of certificate authorities allows the certificateauthorities to be distributed over different geographic locations, whichcan mitigate denial of service attacks that are often location specific.Furthermore, the plurality of certificate authorities can be usedsequentially to form one or more certificate chains to enhance security.The certificate chains can each terminate with the same root certificateauthority. Use of certificate chains can reduce the use of the rootcertificate authority, thereby reducing the risk of compromising theroot certificate authority. The certificates can include the public keyof the certificate authority that issued the certificate and the publickey of the certificate authority that will receive the certificate.

By providing authorization data to the locking device 110 in advance ofa request to gain access to the locking device 110, the method 200 canmitigate delays caused by unreliable connectivity typically experiencedin self-storage facilities.

Returning now to FIG. 2, at step 208, a user may seek to gain access tothe locking device 110 and provide a security command to the lockingdevice 110. The security command can include requesting data identifyingthe user computing device 140. That is, the security command can includeone or more digital access keys to be validated.

In some embodiments, the user computing device 140 provide the securitycommand to the locking device 110 by connecting to the locking device110 via a communication network 130 such as but not limited to aBluetooth® Low Energy network. The user can physically manipulate thelocking device 110, such as pressing a button on the locking device 110,to cause the locking device 110 to begin transmitting advertising datain a Bluetooth® signal. The button on the locking device 110 can be abutton dedicated to begin transmitting a communication signal, or it canbe any other button for operating the lock and be configured to transmita communication signal during operation. The advertising data caninclude identification data for the locking device 110 such as the LoRaMAC address of the locking device 110.

The user computing device 140 can scan for Bluetooth® signals from thelocking devices 110. The scan for Bluetooth® signals can be initiated bya computer program operating on the user computing device 140 thatfacilitates communication between the user computing device 140, theserver 120, and the locking devices 110.

Upon detection of the Bluetooth® signal from the locking device 110, theuser computing device 140 can determine whether the advertising dataincludes a LoRa MAC address that corresponds to any digital access keysstored on the user computing device 140. It the advertising data matchesa digital access key stored on the user computing device 140, the usercomputing device 140 can provide a security command to the lockingdevice 110.

At step 210, the lock processing unit 114 can be configured to determinewhether the security command includes requesting data that correspondsto the authorization data stored in the lock memory 112 for that usercomputing device 140 at step 206. That is, the lock processing unit 114can determine whether the user computing device 140 has provided adigital access key corresponding to the digital access key stored in thelock memory 112.

When the lock processing unit 114 compares the requesting data receivedfrom the user computing device 140 to the authorization data stored inthe lock memory 112, the lock processing unit 114 can determine whetherthe digital access key provided by the user computing device 140corresponds to the authorization data provided to the locking device 110by the server 120. This validation of digital access keys can involvethe locking device 110 and the user computing device 140 exchangingencrypted data using key pairs such as the public/private key pair ofthe user computing device 140.

In some embodiments, the validation of digital access keys can involvethe locking device 110 and the user computing device 140 exchanging aseries of encrypted data. In some embodiments, the data being encryptedcan be random data (i.e., random nonce). In some embodiments, the dataexchanged can be encrypted using the public/private key pair of the usercomputing device 140. In some embodiments, the data exchanged can alsobe encrypted using a session key pair generated by the user computingdevice 140 or the lock processing unit 114. The session key pair can bea temporary key pair that is generated when the user computing device140 is in the vicinity of the lock processing unit 114 and seeks to gainaccess.

For example, the user computing device 140 can generate a session keypair and send the public key to the locking device 110. Upon receipt ofthe public key of the user computing device 140's session key pair, thelock processing unit 114 can also generate a session key pair belongingto the locking device 110 and send the public key of its own session keypair to the user computing device 140.

Upon receipt of the public key of the locking device's 110 session keypair, the user computing device 140 can encrypt the digital access keyreceived from the server 120 (i.e., tenant access key, surrogate accesskey, or master access key) using one of, or both of the session keypairs—that is, the public key of the session key pair of the lockingdevice 110 and/or the private key of the session key pair of the usercomputing device 140. The user computing device 140 can send theencrypted digital access key (i.e., tenant access key, surrogate accesskey, or master access key) to the locking device 110.

Upon receipt of the encrypted digital access key (i.e., tenant accesskey, surrogate access key, or master access key) from the user computingdevice 140, the lock processing unit 114 can decrypt the digital accesskey using the private key of the session key pair of the locking device110 and/or the public key of the session key pair of the user computingdevice 140. The lock processing unit 114 can validate the digital accesskey by determining whether it corresponds to authorization data receivedfrom the server 120 and stored in the lock memory 112.

Determining whether the digital access key corresponds to authorizationdata involves determining whether the digital access key is valid. Thelock processing unit 114 can determine whether the current date and timeis after the pre-determined start date of the digital access key, ifany. In addition, the lock processing unit 114 can determine whether thedigital access key has expired or been expended based on thepre-determined expiration date, pre-determined expiration period, andpre-determined usage limit, if any. The lock processing unit 114 canalso determine whether the digital access key has been revoked, based onthe digital key identifier.

If the lock processing unit 114 determines that the digital access keyis valid, the lock processing unit 114 can encrypt a random nonce usingthe private key of the session key pair of the locking device 110 and/orthe public key of the session key pair of the user computing device 140.The lock processing unit 114 can send the encrypted random nonce to theuser computing device 140.

Upon receipt of the encrypted random nonce from the locking device 110,the user computing device 140 can decrypt the random nonce using thepublic key of the session key pair of the locking device 110 and/or theprivate key of the session key pair of the user computing device 140.The user computing device 140 can sign the random nonce using theprivate key corresponding to the public key of the user computing device140 included in the digital access key and provided by the server 120,that is, the private key of the public/private key pair generated uponinstallation of a computer program to facilitate communication betweenthe user computing device 140, the server 120, and the locking devices110. The user computing device 140 can encrypt the signed random nonceusing the public key of the session key pair of the locking device 110and/or the private key of the session key pair of the user computingdevice 140. The user computing device 140 can send the encrypted, signedrandom nonce to the locking device 110.

Upon receipt of the encrypted, signed random nonce from the usercomputing device 140, the locking device can decrypt the signed, randomnonce using the private key of the session key pair of the lockingdevice 110 and/or the private key of the session key pair of the usercomputing device 140. The lock processing unit 114 can verify whetherthe random nonce is the same random nonce that it previously transmittedto the user computing device 140 and whether the random nonce was signedusing by a key corresponding to the public key of the user computingdevice 140 included in the digital access key and provided by the server120. That is, the lock processing unit 114 can verify whether the randomnonce was signed using the private key of the public/private key pairgenerated upon installation of a computer program to facilitatecommunication between the user computing device 140, the server 120, andthe locking devices 110. If verified, the lock processing unit 114 candetermine that the user computing device 140 is authorized and themethod 200 can proceed to step 212.

If the lock processing unit 114 determines that the user computingdevice 140 is not authorized (i.e., any one of the digital access keyreceived from the server 120 being invalid, the random nonce receivedfrom the user computing device 140 being different from the random noncegenerated by the lock processing unit 114, or the random nonce was notsigned by a key corresponding to the public key of the user computingdevice 140 included in the digital access key and provided by the server120), the method 200 can proceed to step 214.

At step 212, in response to determining that the requesting datacorresponds to the authorization data stored for the user computingdevice 140, the lock processing unit 114 can be configured to generate acontrol signal for the actuator 118 based at least in part on thesecurity command. If the security command is an unlock command, the lockprocessing unit 114 can generate a control signal for the actuator 118to move the locking device 110 into the unlocked state. If the securitycommand is a lock command, the lock processing unit 114 can generate acontrol signal for the actuator 118 to move the locking device 110 intothe locked state.

At step 214, in response to determining that the requesting data doesnot correspond to the authorization data stored for the user computingdevice 140, the lock processing unit 114 can terminate communicationwith the user computing device 140.

Reference will now be made to FIGS. 3, 4A, and 4B simultaneously. FIG. 3illustrates an example scenario 300 for requiring access to a securespace and FIGS. 4A and 4B illustrate an example method 400 of requestingaccess to a secure space, according to at least one embodiment. In thisexample, the secure space is a self-storage unit.

In scenario 300, a tenant has stored items in their self-storage unit ata self-storage facility 302 b. The tenant is the only user with accessto the self-storage unit. A trusted third-party requires an item storedin the tenant's self-storage unit. However, the tenant is located in afirst location 302 a and cannot conveniently go to the self-storage unitto retrieve the item. Furthermore, the tenant's key is located at thetenant's home, a second location. The trusted third-party does not haveaccess to the tenant's home to retrieve the key. The tenant trusts thethird-party with access to the self-storage unit but the third-party wasnot setup on the self-storage unit account because the tenant did notforesee that the third-party would require access.

In method 400, at step 402, the trusted third-party can download andexecute the computer program onto their user computing device 440 tofacilitate communication with the server 120 from their user computingdevice 440. The trusted-third party may use the computer program setupan account. At step 404, the tenant can use the computer program ontheir user computing device 440 to share access with the trustedthird-party. More specifically, the tenant can initiate the generationand transmission of a digital authorization token 442 to the trustedthird-party's user computing device 440 to allow the trustedthird-party's user computing device 440 to submit a security command tothe locking device 410 (shown in FIG. 4B) for the tenant's self-storageunit.

At step 406, the trusted third-party can go to the site of theself-storage unit 302 b. Using their user computing device with thecomputer program operating therein, the trusted third-party can obtainaccess through the main access gate, locate the tenant's self-storageunit 444 a, and submit a security command to unlock the locking device410. The security command from the user computing device can becommunicated wirelessly to the locking device 110, via the communicationnetwork 130. The communication network 130 can include one or more nodes432 for transmitting and receiving data from the components of thesystem 100 located in a facility including user computing devices 432.LoRa, Bluetooth® or Bluetooth® Low Energy can be used to communicate thesecurity command from the user computing device 440 to the lockingdevice 110.

The security command can be processed by the locking device 110. Thesecurity command can include requesting data, such as digital accesskeys, a password passcode, or fingerprint data that are related useraccount information. The locking device 110 can determine whether thesecurity command may be granted, based on whether the requesting datacorresponds to authorization data stored in the lock memory 112.

When the security command is granted, the locking device 110 generates acontrol signal for the actuator based on the security command. Forexample, for an unlock command, the locking device 410 unlocks and thetrusted third-party is able to pull down the body of the locking device410, releasing the shackle so the locking device 410 can be removed andthe door to the self-storage unit can be opened. If authorization datafor the locking device 410 b indicated that the tenant's account was inpoor standing (i.e., virtually overlocked), then the digital access keywill be found invalid, the security command will not be granted and thecontrol signal is not generated. An account may be in poor standing fornon-payment of rental fees and other issues.

Referring now to FIG. 5, shown therein is an illustration 500 of datathat can be made available by the system 100 to central managers,according to at least one embodiment.

The central managers can review statuses of user accounts (i.e.,customer profile management), access management data and metrics, orsystem alerts generated based on monitoring data. The central managerscan access this data on-site or remotely from a user computing device140 via a web portal or a computer program.

Referring to FIG. 6, shown therein is an illustration 600 of differentstatuses that secure spaces can have, according to at least oneembodiment. In this example, the secure space is a self-storage unit.The status of the self-storage units at a site can be illustrated in amapping tool of the computer program for central managers. Statusesillustrated can include, but is not limited to: (1) occupied andaccessible (i.e., good standing) 610; (2) occupied and virtuallyoverlocked (i.e., poor standing) 620; and (3) vacant 630. Each of thestatuses in the mapping tool can also be color coded. For example,occupied and accessible 610 can be green; occupied and virtuallyoverlocked 620 can be red; and vacant 630 can be blue.

Referring to FIG. 7, shown therein is an illustration of differentpermissions to secure spaces, according to at least one embodiment. Inthis example, the secure space is a self-storage unit. When aself-storage unit is occupied and in good standing 610, the self-storageunit is accessible by the tenant and any trusted third-parties that thetenant provides access to. When a self-storage unit is occupied and inpoor standing 620, the self-storage unit is not accessible by the tenantor any trusted third-parties, including the tenant, until theself-storage unit is returned to good standing. In the meantime, theself-storage unit is accessible by central managers including anadministrator and site manager. When a self-storage unit is vacant 630,it is available for rental and accessible by central managers includingan administrator and site manager.

Referring to FIG. 8, shown therein is an illustration 800 of a usercomputing device of central managers having control of multiple sites,according to at least one embodiment. A computer program operating onthe user computing device of a central manager can access data andanalytics from all sites, including, but not limited to access frequencyinformation, site vacancy statistics, sales throughput, alert and errornotices, and geoanalytics.

The systems and methods disclosed herein can allow for continuousmonitoring of the secure space. For example, the server processing unit124 can generate alerts based on analysis of the operating data of thelocking devices 110 and/or the monitoring data of the secure space. Thealerts can be transmitted to a central manager at a user computingdevice 140. A central manager can include personnel located on-site(i.e., local) or off-site (i.e., remote) such as employees, sitemanagers, and corporate administrators.

For example, a user may enter an entrance gate of the facility and thatuser is the only user in the facility. The server processing unit 124can identify a locking device 110 and a storage unit associated with theuser account of the user. If a locking device 110 that is not associatedwith the user account communicates operating data indicating that thelocking device 110 is being manipulated, then an alert can be triggered.In some embodiments, the alert can be automatically transmitted to theuser to let them know that they are at the wrong unit or the wrongfloor.

In some embodiments, the alert can also cause image data, includingvideo data, to be automatically provided to a site manager. The sitemanager may not be on site at the time and can view the alert and theimage data on a user computing device 140 to assess the situation. Ifthe site manager observes that the user appears to be innocentlyattempting to access the wrong unit, the site manager can send a messageto the user to assist and/or guide them to the correct unit. Forexample, the site manager can let the user know that they are on thewrong floor.

Alerts can be triggered based on any event including but limited totimed events, unexpected behavior, or missing events. For example, auser can enter the site and unlock their self-storage unit. If a longduration, such a several hours, passes without a locking event, an alertmay be triggered. In another example, when two distinct users enter themain gate and only one locking device 110 is unlocked, an alert may betriggered. In another example, once the user enters the site, alerts canbe provided to guide the user to their self-storage unit. Morespecifically, upon entering the site, communication from the usercomputing device 140 to nodes of the communication network 130 can beused to determine the location of the user. For example, the alerts canprovide directions including but not limited to “continue to the end ofthe hallway”, “turn left”, “turn right”, “take the elevator”, etc. . . .

In another example, an alert may be triggered when the locking device110 is in the locked state but also the open state. This can occur ifthe locking device 110 has been physically tampered with, such as cut orbroken, which is typically performed by someone who does not have, orcannot obtain authorization to unlock the locking device 110 (e.g.,theft or tenant in poor standing circumventing an overlock).

In another example, an alert may be triggered when the locking device110 is in the closed state but also the unlocked state for some periodof time. This can occur if a user has physically closed the lockingdevice 110 and failed to provide a command to lock the locking device110. That is, after a locking device 110 is physically closed, thesystem can expect to receive a locking command within some period oftime. After such time has elapsed without receipt of a locking command,the alert can be triggered. This can occur when, for example, a usersimply forgets to provide the command, or if a failure occurs in thetransmission of the lock command between the user computing device 140,the server 120, and the locking device 110.

The server processing unit 124 can update the authorization data basedon the access management data, monitoring data and/or informationreceived from the user. For example, when a tenant moves out, the tenantmay submit a vacancy notice. A vacancy notice can include capturingimage data of the empty secure space and transmitting the image data tothe server 120. The server processing unit 124 can operate an imageprocessing application to assess whether the received image data showsan empty secure space. If the server processing unit 124 determines thatthe secure space is empty, the authorization data for that lockingdevice 110 can be updated from an occupied in good standing status to avacant status. In this manner, the secure space can be placed in avacant status without manual input.

In some embodiments, the server processing unit 124 can also process theimage data to verify identifying information, such as a unit number. Insome embodiments, the server processing unit 124 can also processmetadata related the image data to confirm the location that the imagedata was captured, or the time that the image data was captured. In someembodiments, the image data can be captured by other system componentssuch as sensor units (described in more detail below).

In some embodiments, alerts can relate to authorization data. The serverstorage unit 122 can store a list of user accounts to be notified when aparticular, or a type of secure space becomes vacant. For example, someusers be looking to rent a self-storage unit and others may be lookingfor a larger self-storage unit. When a secure space becomes availablefor rent, that is, when the status of the corresponding locking device110 becomes vacant, an alert can be transmitted to user accounts whowish to be notified. Users may then rent the vacant self-storage unitfrom the computer program executing on the user computing device 140.Upon the new tenant completing the rental process such as agreeing to arental agreement, providing payment, and any other requisites, theserver processing unit 124 can update the authorization data for thatlocking device 110 from the vacant status to the occupied in goodstanding status.

Corporate administrators, including district managers, can have accessto multiple servers 120 that manage individual facilities or a singleserver 120 that is configured to manage multiple facilities. An accountassociated with a corporate administrator can have different analyticsand views from what the site managers can view. However corporateadministrators and site managers can have a similar level of access andcontrol. In particular, corporate administrators and site managers caneach have the ability to block access to (i.e., virtually overlock) anindividual locking device.

Referring to FIGS. 9A-9E, illustrated therein are perspective views of alocking device 900 in a closed state, according to at least oneembodiment.

FIG. 9A shows the locking device 900 as a pad lock that includes a body902 and shackle 903 Shackle 903 has two arms 904 a and 904 b and isarranged to be movable between a closed position (see for example FIGS.9A-9E) wherein bottom portions of both of the arms 903 a and 903 b aresecured within the body 902 and an open position (see FIG. 12) whereinthe bottom portion of one of the arms 904 is secured within the body 902and the other one of the arms 904 is withdrawn from the body 902. Whenthe locking device 900 is in the closed position (see for example FIGS.9A-9E), the locking device 900 can be in either a locked state, apartially locked state, or an unlocked state. It should be noted thatlocking device 900 should not be limited to being a pad lock. Lockingdevice 900 could be another type of lock including but not limited to acam lock, a cylinder lock, a tubular lock, a pin tumbler lock, or thelike.

In at least one embodiment, the shackle 903 can be a part of anelectrical circuit and an electrical current can be applied to theshackle 903. When the shackle 903 is closed, the electrical circuit mayform a closed loop and provide a signal indicating that the lockingdevice 900 is in the closed state. However, when the electrical circuitdoes not form a closed loop, that is, when the shackle 903 is open orcut, the signal indicating the shackle 903 is in the closed position isnot provided, indicating that locking device 900 is in the open state.Further details are provided below. In at least one embodiment, thecircuit may be an optical circuit may be included to indicate the stateof the shackle 903. For instance, in at least one embodiment, thecircuit could be an optical circuit such as but not limited to a lightpipe or a light tube, where a light source and a detector are configuredto indicate the state of the shackle 903.

Referring now to FIG. 9E, illustrated therein is a cross-sectional viewfrom top to bottom of the locking device 900 of FIGS. 9A and 9D alongthe line A-A shown in FIG. 9D. FIG. 9E shows the main internalcomponents of the locking device 900 when the locking device 900 is in aclosed and a locked state, according to at least one embodiment.

Body 902 includes a rotatable locking cam 906 and a locking pin 908.Rotation of the rotatable locking cam 906 controls engagement of thelocking pin 908 with a groove 910 of one of the arms 904 of the shackle903 when the locking device 900 is in the closed state. When the lockingpin 908 engages the groove 910 of one of the arms 904 of the shackle 903(e.g. arm 904 b), the one of the arms 904 is secured within the body 902and the shackle 903 is retained in its locked position. When the lockingpin 908 disengages the groove 910 of the one of the arms of the shackle903 (e.g. arm 904 b), the one of the arms 904 is secured within the body902 and the shackle 903 is free to move to its unlocked position.Rotation of rotatable locking cam 906 is controlled by a drive system(described below).

Rotatable locking cam 906 includes a locked paddle 911 and an unlockedpaddle 912. In at least one embodiment, each of the locked paddle 911and the unlocked paddle 912 extend towards the one of the arms 904 (e.g.arm 904 b) of the shackle 903. In at least one embodiment, locked paddle911 and unlocked paddle 912 may be made of a non-magnetic material. Inat least one embodiment, locked paddle 911 and unlocked paddle 912 maybe made of a magnetic material. Locked paddle 911 is typicallypositioned vertically above the unlocked paddle 912 in a directiontowards a top end of the locking device 900, however, in at least oneembodiment, the locked paddle 911 may be otherwise configured relativeto unlocked paddle 912. As shown in FIG. 9E, when the locking device 900is in the locked position, the locked paddle 911 directly engages thelocking pin 908 and supports the locking pin 908 to engage groove 910 ofthe shackle 903.

As shown in FIG. 9E, when the locked paddle 911 of the rotatable lockingcam 906 directly engages the locking pin 908, the locking pin 908 isengaged with a groove 910 of one of the arms 904 of the shackle 903 andthe one of the arms 904 of the shackle 903 is retained within the body902. At this position, the locking device 900 is in a locked state.

Body 902 also includes a power supply 920 (e.g. battery) for supplyingelectrical power to the drive system (described below).

Turning to FIG. 10, as the locking cam 906 rotates away from the lockedposition relative to the shackle 903, for example in a counter-clockwisedirection, (e.g. upwardly relative to shackle 903 and/or the body 902),the locked paddle 911 disengages from the locking pin 908. In FIG. 10,the locking pin 908 is shown in the locked position when it is engagedwith the groove 910 of the shackle 903. In this position, the lockingdevice 900 is in a partially locked state. As a user, for example,applies a force to the shackle 903 to move the shackle 903 from theclosed position to the open position (thereby withdrawn from the body902), the locking pin 908 will disengage from the groove 910 and shiftlaterally relative to the arm 904 of the shackle 903 (e.g. in a leftdirection as shown in FIG. 10).

Turning to FIG. 11, illustrated therein is an embodiment of the lock 900of FIGS. 9A-9E where the locking pin 908 is shown to be open (i.e.disengaged from the groove 910 of the shackle 903). In at least oneembodiment, the locking pin 908 can disengage from the groove 910 andshift laterally relative to the arm 904 of the shackle 903 in responseto the shackle 903 being pulled upwardly (e.g. the upward force appliedto the shackle 903 translates to a lateral force on the groove 910 thatpushes the pin laterally away from the shackle). In at least oneembodiment, the locking pin 908 can disengage from the groove 910 andshift laterally relative to the arm 904 of the shackle 903 by gravity.In at least one embodiment, the locking pin 908 can disengage from thegroove 910 and shift laterally relative to the arm 904 of the shackle903 by the action of a biasing device, such as but not limited to aspring or a magnetic actuator (e.g. the locking pin 908 is made of amagnetic material and a magnetic actuator pulls or pushes the pinlaterally).

Referring now to FIG. 12, illustrated therein is another embodiment oflock 900 including two detection switches 914. In this embodiment, onedetection switch 914 is positioned to detect the position of each arm904 of the shackle 903. For instance, as shown in FIG. 12, detectionswitch 914 a is positioned below arm 904 a when arm 904 a is received inthe body 902 of the lock 900 and detection switch 914 b is positionedbelow arm 904 b when arm 904 b is received in the body 902 of the lock900.

Each detection switch 914 is configured to have to a first state toindicate when the shackle 903 is in its open state and a second state toindicate when the shackle 903 is in its closed state. For instance, asshown in FIG. 12, first detection switch 914 a is in its first state toindicate that the arm 904 a of shackle 903 is in its open state.Similarly, second detection switch 914 b is in its first state toindicate that the arm 904 b of shackle 903 is in its open state.

Each of the detection switches 914 may be coupled (e.g. electricallycoupled) to the locking processing unit of the lock 900 to provide asignal to the locking processing unit indicating a position of theshackle 903 (e.g. of the arms 904 of the shackle 903). The lockprocessing unit may determine a status of the shackle (e.g. as beingeither open or closed) based on the signal received from one or more ofthe detection switches 914. For example, in the embodiment shown in FIG.13 where the shackle 903 has been cut, the first detection switch 914 aindicates that arm 904 a of the shackle 903 is in its open state andsecond detection switch 914 b indicates that arm 904 b of the shackle903 is in its closed state. It should be noted that in this position,the locking pin 908 and the locking cam 906 are each still in theirrespective locked positions, however, the locking processing unit isable to determine the position of the shackle based on the signalreceived from one or more of the detection switches.

In at least one embodiment, the detection switches 914 areelectromechanical switches, such as but not limited to KSC4D SeriesSealed Detect Switches by C&K®.

FIG. 14 shows three diagrams of potential configurations for a shackledetection switch circuit for providing the position of the shackle 903to the locking processing unit can be configured in a number ofdifferent ways. Although FIG. 14 provides three possible configurations,it should be understood that other configurations are contemplated inthe embodiments described herein and the embodiments described hereinshould not be limited by the configurations shown in FIG. 14.

For instance, as shown in FIG. 14, in at least one embodiment, theshackle detection switch circuit may include two switches connected inseries. In this embodiment, if one of the switches is broken (e.g.changes state) the circuit switches its state.

In at least one embodiment, the shackle detection switch circuit mayinclude a separate circuit for each switch of the locking device. Inthis embodiment, if one of the switches is broken, only the circuitconcluding that switch will change state.

In at least one embodiment, the shackle detection switch circuit mayinclude a single circuit with a single switch. In this embodiment, ifthe switch is broken, the circuit will change state.

Other mechanisms for providing the shackle detection switch circuit mayinclude a light circuit through a light pipe running through theshackle. The light circuit may include a light emitting diode (LED), forexample, at one end of the shackle and a detector positioned opposed tothe end of the LED within the body 902 of the locking device 900. Inthis embodiment, if the shackle 903 is cut the LED will stop emittinglight and the detector can detect the absence of light.

In at least one embodiment, the position of the LED and the detector maybe reversed from that previously described. In this embodiment, theshackle 903 may include the electrical switch so that a connection ateither end of the shackle 903 (e.g. metal shackle) will be broken by anopen or cut event.

FIG. 15A is a cross-sectional view of another embodiment of the lockingdevice 900 in a locked state with a front panel of the locking device900 removed to show a drive system 921 of the locking device 900,according to at least one embodiment. Drive system 921 includes a motor922, a gear box 924, a worm gear 926 a cam drive gear 928 and a controlprinted circuit board (PCB) 930. In at least one embodiment, the motor922 and the cam drive gear 928 drive the locking cam 906 between thelocked and unlocked positions. FIG. 15B is a reversed view of FIG. 15Ashowing the locking device 900 of FIG. 15A with a rear panel removed.

In this embodiment, a signal generated by the PCB 930 activates themotor 922 to rotate the rotatable locking cam 906. Activation of themotor 922 rotates the worm gear 926 via the gear box 924, which in turnrotates the cam drive gear 928 to rotate the rotatable locking cam 906.A subsequent signal from the PCB 930 can turn off the motor 922.

In at least one embodiment, the position of the rotatable cam 906 can bedetected by for example but not limited to hall detect sensors and/ormagnets.

For example, a Hall detect sensor (i.e. a transducer that varies itsoutput voltage in response to a magnetic field) could be used to detectsif locking device 900 is in an unlocked state by detecting if therotatable locking cam 906 has rotated to a position where the lockingpin 908 is disengaged with the groove 910. In these embodiments, a halldetect sensor could also detect if locking device 900 is in a lockedstate by detecting if the locking pin 908 is in a position where it isengaged with the groove 910. In another embodiment, a hall detect sensorcould detects if locking device 900 is in a locked state by detecting ifthe rotatable locking cam 906 has rotated to a position where thelocking pin 908 is engaged with the groove 910. In each of theseembodiments, the one or more hall detect sensors may be mounted on thePCB.

In at least one embodiment, a position of the locking pin 908 can bedetected based on the position of a biasing mechanism, such as but notlimited to a spring. In at least one embodiment, a position of thelocking pin 908 can be detected using one or more magnets that areconfigured to bias the locking pin 108, for example, either towards oraway from the rotatable locking cam 906 and/or towards or away from theshackle 903.

In at least one embodiment, the position of one or more of the lockingcam 906, the locking pin 908 and the shackle 903 may be used todetermine whether the lock is in one or more of its locked, unlocked,open or closed states. In some embodiments, upon determining whether thelock is in one or more of its locked, unlocked, open or closed states,the locking device 900 may, together with the lock communicationinterface, may send an alert to a user (e.g. to a mobile device of theuser via Bluetooth or the like) to indicate whether the lock is in oneor more of its locked, unlocked, open or closed states. For instance,the locking device 900 may send an alert to a mobile device of a user asthe user leaves the lock and walks away.

FIG. 16A shows a cross-sectional view of another embodiment of lockingdevice 900 having a shackle 903 having a locking pin groove 910 sizedand shaped to receive a locking pin 908 of the locking device 900. Inthis embodiment, shackle 903 also includes a raceway 925 positionedabove the locking pin groove 910. Raceway 925 is sized and shaped toengage with a spring ball plunger 926 of the locking device 900. Asshown in FIG. 16A, in at least one embodiment, the spring ball plunger926 is positioned upward relative to the locking cam 906 of the lockingdevice 900 to engage with arm 904 b of shackle 903.

Raceway 925, shown in greater detail in FIG. 16B, provides for a cut ordamaged shackle 903 to be removed from the locking device 900. Forinstance, by rotating the shackle 903 when it is in its open positionsuch that the spring ball plunger 926 follows the path of the raceway925, and then pulling upwardly on the shackle 903 while depressing theplunger, the shackle 903 can be removed from the body 902 of the lockingdevice 900 without having to open the structure (e.g. one or morepanels) of the locking device 900. Further, by inserting a new shackle903 into the recess of the body 902 adjacent to the spring ball plunger926 such that the spring ball plunger 926 enters the raceway 925 of theshackle 903, a new shackle 903 can be installed in the reverse pathwithout having to open the structure (e.g. one or more panels) of thelocking device 900. Accordingly, raceway 925 provides for shackle 903 totranslate upward and rotate about 90 degrees (in either direction) oncethe other end (e.g. arm 904 a) is vertically translated upwardly by adistance to provide for it to clears the lock body 902 upon beingrotated.

Raceway 925 may also work together with the one or more shackle detectswitches 914 to close and lock the shackle 903. For instance, in atleast one embodiment, shackle 903 needs to be positioned within the body902 to provide for both switches 924 to be engaged. In one example, onemight attempt to imitate that lock 900 is locked when it is not closedby unlocking and opening the locking device 900, then cutting theshackle 903 and reinserting the shackle 903 into the body 902 to closethe switch while putting the lock 900 into its locked state. In thiscase, locking device 900 may detect that the switch has been released,detect a changed state of the locking device 900 and transmit a message(e.g. to the server).

Various embodiments have been described herein by way of example only.Various modification and variations may be made to these exampleembodiments without departing from the spirit and scope of theinvention, which is limited only by the appended claims. Also, in thevarious user interfaces illustrated in the figures, it will beunderstood that the illustrated user interface text and controls areprovided as examples only and are not meant to be limiting. Othersuitable user interface elements may be possible.

1. A system for controlling access to a secure space, the systemcomprising: at least one communication network; a locking devicefastenable to an access point of the secure space, the locking devicecomprising an actuator, a lock processor, a lock memory, and at leastone lock communication interface, the actuator for moving the lockingdevice into a locked state to maintain the access point closed or anunlocked state to allow the access point to be opened, the lockprocessor operable to generate a control signal for the actuator, the atleast one lock communication interface being operable to communicate viathe at least one communication network; and a server comprising: aserver storage unit to store authorization data for the locking device;at least one server communication interface operable to communicate withthe locking device and at least one user computing device via the atleast one communication network; and a server processing unit operableto: receive, from a user computing device of the at least one usercomputing device, a request to access the locking device; authenticatethe user computing device; generate authorization data for the lockingdevice and the user computing device; and provide at least part of theauthorization data to each of the locking device and the user computingdevice; wherein the lock processor is operable to: store theauthorization data from the server in the lock memory; receive asecurity command from the at least one user computing device; determinewhether the security command comprises requesting data that correspondsto the authorization data stored in the lock memory; and in response todetermining that the requesting data corresponds to the authorizationdata stored in the lock memory; generate a control signal for theactuator to move the locking device into the locked state when thelocking device transitions from open to closed, otherwise generate acontrol signal for the actuator based at least in part on the securitycommand.
 2. The system of claim 1, wherein: the security commandcomprises either an unlock command or a lock command; upon receipt of anunlock command, the control signal generated by the lock processorcomprises a signal to move the locking device into the unlocked state;and upon receipt of a lock command, the control signal generated by thelock processor comprises a signal to move the locking device into thelocked state.
 3. The system of claim 1, wherein the authorization dataprovided to the user computing device comprises a public key of apublic/private key pair of the locking device, the private key pair ofthe locking device being stored in the lock memory.
 4. The system ofclaim 1, wherein the authorization data provided to the user computingdevice comprises a public key of a public/private key pair of the usercomputing device, the private key pair of the user computing devicebeing stored in memory of the user computing device.
 5. The system ofclaim 1, wherein the authorization data provided to the locking deviceand the user computing device comprises a digital access key including apre-determined usage limit; and the lock processor is operable todetermine whether the digital access key is valid based on thepre-determined usage limit.
 6. The system of claim 5, wherein thedigital access key includes at least one of a pre-determined expirationdate or a pre-determined expiration period; and the lock processor isoperable to determine whether the digital access key is valid based onat least one of the pre-determined expiration date and thepre-determined expiration period.
 7. The system of claim 1, wherein theauthorization data comprises a digital access key including at least oneof a generation date or a pre-determined start date; and the lockprocessor is operable to determine whether the a digital access key isvalid based on at least one the generation date or the pre-determinedstart date.
 8. The system of claim 1, wherein the authorization datacomprises a digital access key signed using a certificate; and the lockprocessor is operable to determine whether the digital access key isvalid based on the certificate used to sign the digital access key. 9.The system of claim 1, wherein the certificate is generated by acertificate authority of a plurality of sequential certificateauthorities.
 10. The system of claim 1, wherein the server processingunit operable to authenticate the user computing device comprisesgenerating an invitation token having a pre-determined expirationperiod, sending the invitation token to the user computing device, andreceiving the invitation token within the pre-determined expirationperiod. 11.-20. (canceled)
 21. A locking device comprising: a bodyincluding: a rotatable locking cam having a locked paddle and anunlocked paddle, the rotatable locking cam being rotatable between alocked position and an unlocked position; a locking pin; and a powersupply for supplying electrical power to circuit components of thelocking device; and a shackle having two arms insertable into the body,one of the two arms having a groove in a bottom portion thereofconfigured to engage with the locking pin when the rotatable locking camis in the locked position and the shackle is in a closed position;wherein the locking device is configured to detect a position of one ormore of the rotatable locking cam, the locking pin and the shackle. 22.A locking device comprising: a body including: a rotatable locking camhaving a locked paddle and an unlocked paddle, the cam being rotatablebetween a first position and a second position; a locking pin; and apower supply for supplying electrical power to circuit components of thelocking device; and a shackle having two arms insertable into the body,one of the two arms having a groove in a bottom portion thereofconfigured to engage with the locking pin when the shackle is in aclosed position; wherein in the first position, the locked paddle of therotatable locking cam engages the locking pin to retain the locking pinin the groove and in the second position the locked paddle of therotatable locking cam is disengaged from the locking pin.
 23. Thelocking device of claim 21, wherein the locking pin is configured tofall out of the groove of the shackle when the rotatable locking uponthe shackle moving upwardly relative to the locking pin.
 24. The lockingdevice of claim 21, wherein the body includes one or more switchesconfigured to indicate if the shackle is in an open or a closedposition.
 25. The locking device of claim 24, wherein the body includestwo switches, one positioned at either end of the shackle to indicate ifthe shackle is in an open or a closed position.
 26. The locking deviceof claim 25, wherein the switches are two stage switches.
 27. Thelocking device of claim 21, wherein the body further includes a springball plunger and the shackle further includes a raceway, the spring ballplunger being configured to rest within the raceway to provide for theshackle to be removed from the body.
 28. The locking device of claim 21,wherein each of the unlocked paddle and the locked paddle extend fromthe rotatable locking cam towards a same arm of the shackle.
 29. Thelocking device of claim 21, wherein the locked paddle is positionedvertically above the unlocked paddle.
 30. The locking device of claim21, wherein the rotatable locking cam is configured to rotate in a firstdirection to move the locking device from a locked state to an unlockedstate and a second direction to move the locking device from an unlockedstate to a locked state.